v5.8.2

Compare Source

Patch Changes

• #​2285 20c1b38 Thanks @​dustinbyrne! - getFeatureFlag and isFeatureEnabled now respect the sendFeatureFlagEvent client option if not explicitly specified when called.

• #​2285 20c1b38 Thanks @​dustinbyrne! - The sendFeatureFlagEvents option for getFeatureFlagPayload is now marked as deprecated as it is not used.

v5.8.1

Compare Source

Patch Changes

• #​2243 1981815 Thanks @​hpouillot! - - fix error handling on process crash
  • fix exception flushing
• Updated dependencies [1981815]:
  • @​posthog/core@​1.0.2

v5.8.0

Compare Source

Minor Changes

• #​2219 44d10c4 Thanks @​daibhin! - add exception rate limiter

Patch Changes

• Updated dependencies [44d10c4]:
  • @​posthog/core@​1.0.1

v5.7.0

Compare Source

Minor Changes

• #​2218 cfe1e94 Thanks @​oliverb123! - Added before_send function

v5.6.0

Compare Source

1. Added support for filtering feature flags with flagKeys parameter in sendFeatureFlags options

v5.5.1

Compare Source

1. wrap InconclusiveMatchErrors in logMsgIfDebug for local flag evaluations on sendFeatureFlags

v5.5.0

Compare Source

1. feat: make the sendFeatureFlags parameter more declarative and ergonomic. Implementation notes below:

Modified sendFeatureFlags to be type boolean | SendFeatureFlagsOptions, (which is defined thusly)

export interface SendFeatureFlagsOptions {
  onlyEvaluateLocally?: boolean
  personProperties?: Record<string, any>
  groupProperties?: Record<string, Record<string, any>>
}

This lets users declare (1) whether to use local evaluation, and (2) which properties to supply explicitly for that evaluation, every time they want to send feature flags. It also supports the old boolean behavior if folks don't care and would rather the SDK infer it.

Now, you can make calls like this

posthog.captureImmediate({
  distinctId: 'user123',
  event: 'test event',
  sendFeatureFlags: {
    onlyEvaluateLocally: true,
    personProperties: {
      plan: 'premium',
    },
  },
  properties: {
    foo: 'bar',
  },
})

or simply

posthog.captureImmediate({
  distinctId: "user123",
  event: "test event",
  sendFeatureFlags: true // this will still infer local evaluation if it appears to be configured, but it won't try to pull properties from the event message
  properties: {
    foo: "bar",
  },
});

v5.4.0

Compare Source

feat: respect local evaluation preferences with sendFeatureFlags; add property overrides from the event to those local computations so that the locally evaluated flags can be more accuratee. NB: this change chagnes the default behavior of capture and captureImmediately – we will now only send feature flag data along with those events if sendFeatureFlags is explicitly specified, instead of optimistically sending along locally evaluated flags by default.

v5.3.1

Compare Source

1. feat: decouple feature flag local evaluation from personal API keys; support decrypting remote config payloads without relying on the feature flags poller

v5.2.1

Compare Source

1. feat: add captureExceptionImmediate method on posthog client

v5.1.1

Compare Source

1. fix: Handle double-encoded JSON payloads from the remote config endpoint

v5.1.0

Compare Source

1. chore: use /flags?v=2&config=true instead of /decide?v=4 for the flag evaluation backend

v5.0.0

Compare Source

Removed

1. Remove is_simple_flag from PostHogFeatureFlag type
2. Remove captureMode in favor of json capture mode only
3. Remove deprecated personProperties and groupProperties in favor of setPersonPropertiesForFlags and setGroupPropertiesForFlags

Breaking changes

1. feat: migrate to native fetch, Node 20+ required
2. PostHog Node now compresses messages with GZip before sending them to our servers when the runtime supports compression. This reduces network bandwidth and improves performance. Network traffic interceptors and test assertions on payloads must handle GZip decompression to inspect the data. Alternatively, you can disable compression by setting disableCompression: true in the client configuration during tests.